-- Network Working Group J. Case
-- Request for Comments: 2272 SNMP Research, Inc.
-- Obsoletes: 2262 D. Harrington
-- Category: Standards Track Cabletron Systems, Inc.
-- R. Presuhn
-- BMC Software, Inc.
-- B. Wijnen
-- IBM T. J. Watson Research
-- January 1998-- Message Processing and Dispatching for the
-- Simple Network Management Protocol (SNMP)SNMP-MPD-MIB DEFINITIONS::=BEGINIMPORTSMODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF
MODULE-IDENTITY,OBJECT-TYPE,snmpModules,Counter32FROM SNMPv2-SMI;snmpMPDMIB MODULE-IDENTITYLAST-UPDATED"9711200000Z"-- 20 November 1997ORGANIZATION"SNMPv3 Working Group"CONTACT-INFO"WG-email: snmpv3@tis.com
Subscribe: majordomo@tis.com
In message body: subscribe snmpv3
Chair: Russ Mundy
Trusted Information Systems
postal: 3060 Washington Road
Glenwood, MD 21738
USA
email: mundy@tis.com
phone: +1 301-854-6889
Co-editor: Jeffrey Case
SNMP Research, Inc.
postal: 3001 Kimberlin Heights Road
Knoxville, TN 37920-9716
USA
email: case@snmp.com
phone: +1 423-573-1434
Co-editor Dave Harrington
Cabletron Systems, Inc.
postal: Post Office Box 5005
MailStop: Durham
35 Industrial Way
Rochester, NH 03867-5005
USA
email: dbh@ctron.com
phone: +1 603-337-7357
Co-editor: Randy Presuhn
BMC Software, Inc.
postal: 1190 Saratoga Ave, Suite 190
San Jose, CA 95120
USA
email: rpresuhn@bmc.com
phone: +1 408-556-0720
Co-editor: Bert Wijnen
IBM T. J. Watson Research
postal: Schagen 33
3461 GL Linschoten
Netherlands
email: wijnen@vnet.ibm.com
phone: +31 348-432-794
"DESCRIPTION"The MIB for Message Processing and Dispatching"::={ snmpModules 11}-- Administrative assignments ***************************************snmpMPDAdmin OBJECTIDENTIFIER::={ snmpMPDMIB 1}snmpMPDMIBObjects OBJECTIDENTIFIER::={ snmpMPDMIB 2}snmpMPDMIBConformance OBJECTIDENTIFIER::={ snmpMPDMIB 3}-- Statistics for SNMP Messages *************************************snmpMPDStats OBJECTIDENTIFIER::={ snmpMPDMIBObjects 1}
snmpUnknownSecurityModels OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of packets received by the SNMP
engine which were dropped because they referenced a
securityModel that was not known to or supported by
the SNMP engine.
"::={ snmpMPDStats 1}snmpInvalidMsgs OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of packets received by the SNMP
engine which were dropped because there were invalid
or inconsistent components in the SNMP message.
"::={ snmpMPDStats 2}snmpUnknownPDUHandlers OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of packets received by the SNMP
engine which were dropped because the PDU contained
in the packet could not be passed to an application
responsible for handling the pduType, e.g. no SNMP
application had registered for the proper
combination of the contextEngineID and the pduType.
"::={ snmpMPDStats 3}
-- Conformance information ******************************************snmpMPDMIBCompliances OBJECTIDENTIFIER::={snmpMPDMIBConformance 1}snmpMPDMIBGroups OBJECTIDENTIFIER::={snmpMPDMIBConformance 2}-- Compliance statementssnmpMPDCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMP entities which
implement the SNMP-MPD-MIB.
"MODULE-- this moduleMANDATORY-GROUPS{ snmpMPDGroup }::={ snmpMPDMIBCompliances 1}
snmpMPDGroup OBJECT-GROUPOBJECTS{
snmpUnknownSecurityModels,
snmpInvalidMsgs,
snmpUnknownPDUHandlers
}STATUScurrentDESCRIPTION"A collection of objects providing for remote
monitoring of the SNMP Message Processing and
Dispatching process.
"::={ snmpMPDMIBGroups 1}END